home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The PC-SIG Library 10
/
The PC-Sig Library - Shareware for the IBM PC and Compatibles (PC-SIG)(Tenth Edition Disks 1-2804)(1991).iso
/
PC_SIGCD
/
04
/
4
/
DISK0442.ZIP
/
READ.ME
< prev
next >
Wrap
Text File
|
1988-11-30
|
5KB
|
94 lines
SPA:WN (Structured Programming Automated: Warnier Notation) is being
distributed in the free-ware mode. We are not attempting to copy
protect it or to limit its distribution by any sales agreement. We do
ask that if you use the program in any productive activity that you send
money (we suggest $50.00 per user machine, but more or less is welcome) to:
Kansas State University Research Foundation
1640 Fairchild Avenue
Manhattan, KS 66502
You'll be supporting research in a deserving and not very rich
institution as well as providing recompense for a fairly long
development process. You may copy this distribution disk for other
interested persons, but be sure to include this file. If you wish to
enhance this product or incorporate it into another product for sale,
make suitable arrangements with the Research Foundation.
The documentation file (SPAWN.DOC) appears on this diskette. It
represents a synthesis of different attempts to explain what SPA:WN is
all about to different user audiences. The first part is for people
unfamiliar with the concepts of structured programming and hierarchical
top-down design. Its purpose is to set the context for the use of
SPA:WN and to explain the advantages of the use of structured constructs
in program development. The next parts concentrate mostly on the
mechanics of the input stream construction, and give an overview of the
development cycle from program conception through coding to long term
maintenance, and provide a few examples of routine applications of SPAWN
for program design and development. Finally, more advanced details
which may be required in various specialized or unusual enviroments are
outlined in the final sections of the document.
From the documentation file, you should be in a position to make
effective use of the SPA:WN system. The SUMMARY.USE file won't make
much sense until the longer description is read. In addition to this
diskette, you'll need a printer and enough memory and disk space to meet
the program's requirements.
Three different forms of the PWARN (for PASCAL WARNIER) program are
provided. The .COM file is executable code. The .PAS file is Turbo
PASCAL source code employed to produce the .COM file. The .WAR file is
the source code for the program in the form of SPA:WN input. If you
'SPAWN PWARN' the *.PUN file will (almost) be the PWARN.PAS file. [The
comments (8*...*8) surround code fragments to be excluded for Turbo
PASCAL and included for PASCAL 8000, and the comments (T*...*T) surround
code fragments to be included for Turbo PASCAL and excluded for PASCAL
8000. Proper enabling/disabling (e.g. by global edit commands) of these
fragments produce exactly PWARN.PAS or its PASCAL 8000 counterpart.]
The SPAWN.BAT file facilitates the execution of the program. It is
invoked by issuing 'SPAWN filename' where filename is the name of a file
(extension must be .WAR) which is an input stream constructed for
SPA:WN. This batch file defines the set of output files (.ECH for the
echo and diagnostic, .DIA for the diagram, .PUN for any target language
source code, and .SRC for any reordered SPA:WN input). A CLEANUP.BAT
file is provided to erase this same set of output files. Invoke it with
'CLEANUP filename'.
The RODGERS.WAR is an example input file, syntactically correct in the
view of SPA:WN, which may be useful in practicing the use of the SPAWN
command and observing its results. The FORTRAN program produced from
RODGERS has never been compiled, so you may find horrible FORTRAN errors
in it. 'SPAWN RODGERS' runs in a 256K machine with 120K of free disk
space.
Running 'SPAWN PWARN' will fail (as provided) if you employ a 360K
floppy disk -- the total volume of the output files exceeds 360K. This
could be repaired by editing SPAWN.BAT to direct files to different
disks. 'SPAWN PWARN' runs all right (as delivered) using a hard disk
system with 600K or so of free space. [PWARN has a number of constants
defined which could be changed to alter output page dimensions.
However, there has been little or no testing of alternative parameter
combinations, and there can be no guarantee that you will succeed in
attempts to redefine the output page dimensions of Warnier diagrams.]
The size of Warnier diagram which can be run depends upon the amount of
memory in your computer system. The entire diagram is held in memory
while PWARN runs, so very large diagrams cannot be run in systems with
small memories. 'SPAWN PWARN' runs for sure in 512K and smaller diagrams
(like RODGERS.WAR) run in 256K machines. We don't know the details of
the function of space requirement vs. diagram size, or the minimum
machine size to run 'SPAWN PWARN'. It is good practice to keep your
Warnier diagrams small, so any memory limitations should be gratefully
accepted as a sign that your diagrams should be subdivided.
Information about bugs and other comments may be sent to:
Kenneth Conrow, Manager, User Services
University Computing Facilities
Cardwell Hall
Kansas State University
Manhattan, KS 66506 (913)532-6311